The previous extension mechanism is preserved

Also, the extension addition mechanism is now working:

from the Terminal:

test-user@jupyter-test-2duser:~/.local/share/code-server$ ls
CachedExtensionVSIXs  CachedExtensions  Machine  User  coder-logs  coder.json  heartbeat  logs  machineid
test-user@jupyter-test-2duser:~/.local/share/code-server$ 

I just need to test the dask-labextension to make sure it dint break anything

Dask-labextension is now fixed:

It seems that fixing the extensions broke the terminal sync with the Jupyterlab terminal (we now get a blank terminal on vscode), trying to fix that.

It seems that fixing the extensions broke the terminal sync with the Jupyterlab terminal (we now get a blank terminal on vscode), trying to fix that.

These components don't seem related not sure why this would be happening.

It seems that fixing the extensions broke the terminal sync with the Jupyterlab terminal (we now get a blank terminal on vscode), trying to fix that.

These components don't seem related not sure why this would be happening.

seems to be a node thing, the terminal is in there but it's not rendered correctly -- I am trying to change the /bin path to point directly to the code-server + node installation (as we have on quansight-beta), I also updated the order of calling the code-server proxy to use the conda env (I think it was being installed in the pip env of the docker image and not the default)

this is the error, for ref.:

[2022-07-06 12:40:58.929] [window] [error] [object Event]: Error: [object Event]
    at Object.E [as ensureError] (https://gcpqhubstages.qhub.dev/user/test-user/vscode/stable-30d9c6cd9483b2cc586687151bcbcd635f373630/static/out/vs/loader.js:3:4182)
    at i._createLoadError (https://gcpqhubstages.qhub.dev/user/test-user/vscode/stable-30d9c6cd9483b2cc586687151bcbcd635f373630/static/out/vs/loader.js:5:8131)
    at i._onLoadError (https://gcpqhubstages.qhub.dev/user/test-user/vscode/stable-30d9c6cd9483b2cc586687151bcbcd635f373630/static/out/vs/loader.js:5:8250)
    at f (https://gcpqhubstages.qhub.dev/user/test-user/vscode/stable-30d9c6cd9483b2cc586687151bcbcd635f373630/static/out/vs/loader.js:5:10089)
    at Object.errorback (https://gcpqhubstages.qhub.dev/user/test-user/vscode/stable-30d9c6cd9483b2cc586687151bcbcd635f373630/static/out/vs/loader.js:5:10445)
    at e.triggerErrorback (https://gcpqhubstages.qhub.dev/user/test-user/vscode/stable-30d9c6cd9483b2cc586687151bcbcd635f373630/static/out/vs/loader.js:3:11144)
    at https://gcpqhubstages.qhub.dev/user/test-user/vscode/stable-30d9c6cd9483b2cc586687151bcbcd635f373630/static/out/vs/loader.js:3:10850
    at HTMLScriptElement.f (https://gcpqhubstages.qhub.dev/user/test-user/vscode/stable-30d9c6cd9483b2cc586687151bcbcd635f373630/static/out/vs/loader.js:3:11365)

So the bug with installing a new extension to vscode is now fixed, though for some reason the inbuilt terminal from the code-server does not work anymore, seems to be a proxy/port-related issue. -- This will be addressed in a future issue